Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Added

• Added Vercel CLI scripts to package.json, including dev:vercel and build:vercel.

Changed

• Bumped project version to v1.18.5.
• Updated generator metadata in app.html to reflect SvelteKit 2.44.0.
• Added scripts/testRedirects.js to .gitignore.
• Cleaned up header in jsconfig.template.jsonc.
• Updated Repository Structure section in README.md.
• Restructured CHANGELOG.md such that sections are presented in alphabetical order.
• Corrected JSDoc annotations in static/disableSw.js.
• Updated dependencies:
  • @sveltejs/kit 2.43.8 → 2.44.0
  • eslint-plugin-jsdoc ^60.8.0 → ^60.8.1

Documentation

• Revised Repository Structure to accurately reflect the folders under /tests.

Removed

• Removed all references to Netlify and all Netlify-specific scripts from package.json.
• Removed test:redirects script from package.json.
• The testRedirects.js script has been removed from version control, as it is no longer needed to test Netlify redirects.

Checklist

• I have read and followed the guidelines in the CONTRIBUTING document.
• I've checked for existing Pull Requests for the same update/change.
• My code follows the project’s coding style.
• My code has been linted locally before submission.
• All new and existing tests pass.

• I have updated the documentation accordingly.
• I have added tests to cover my changes, if applicable. (Optional, especially for new contributors)

Pull requests are part of a collaborative process — we welcome contributions and review each one carefully. For all but the smallest changes, you can expect maintainers to request improvements or clarifications.

Please check back after opening your PR and be responsive to feedback so we can get your contribution merged quickly.

Thanks for helping improve Network Pro Strategies!